-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce virt-xml into disk APIs #394
base: main
Are you sure you want to change the base?
Conversation
Fixed the filesystem, disks still broken: https://logs.cockpit-project.org/logs/pull-394-20210924-130035-1e3d9861-fedora-34/log.html |
1e3d986
to
558838f
Compare
558838f
to
b16aad7
Compare
0faa317
to
b16aad7
Compare
This is currently blocked on virt-manager/virt-manager#311 , as it fails https://logs.cockpit-project.org/logs/pull-394-20211004-110348-b16aad72-fedora-34/log.html#21-2 |
79830af
to
0138180
Compare
The fix landed in upstream virt-manager 26 days ago, but not released yet AFAICS. |
There is already a release in fedora 36 and ubuntu 2204. I can get going with this PR :) |
0138180
to
4d2b944
Compare
4d2b944
to
3e6c3f4
Compare
This now passes on all distros where virt-xml (virt-manager package) is >= 4.0 . I wonder if I should just keep this PR blocked until it's released in the other distros too, or just write an exception/antipattern for it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that using virt-xml
is probably nicer in the long run, as it's a bit more abstract than directly modifying the XML. But as long as this still breaks on so many supported OSes, I feel that we shouldn't land this -- this would appear as a regression. So either we need to support both code paths for now (ugh!), or just shelve this for a while?
fc84e8c
to
5ee713d
Compare
@skobyda this looks still blocked at least for rhel-8-8, as we still update that, but seems like virt-xml is not updated there. |
Yeah I updated this PR last week to see where it still continues to fail. I'd not try to push this until every distro gets new version of virt-xml |
5ee713d
to
bfe9e9f
Compare
This is probably unblocked by now? |
No idea, let's re-trigger |
bfe9e9f
to
8c39698
Compare
addressType = "pci"; | ||
if (busType === "usb" || busType === "scsi" || busType === "sata") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 2 added lines are not executed by any test. Details
// https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_validate.c | ||
addressBus = 0; | ||
if (busType === "usb") | ||
addressType = "usb"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This added line is not executed by any test. Details
Nope, old version of virt-xml is still present on centos-8-stream and rhel-8-*, so this PR will not get merged until we stop supporting those distros |
@martinpitt, @KKoukiou, what's the point of using |
Please reopen if this is still wanted. |
@mvollmer I am severely out of context on this repo but the virt-xml direction was desired as it picks up correct defaults when attaching devices and removes a lot of custom logic from our side. I dont have examples right now handy. |
Ok, convinced. |
No description provided.